Description

• Adds OpenADRVEN agent to 'services' folder including unit test
• Adds pytest-asyncio and pytest-timeout to 'testing' requirements
• Updates ReadTheDocs with OpenADRVEN documentation

Screenshot of ReadTheDocs:

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

I installed this agent on Volttron platform running the 'develop' branch, using a configuration that connected to our test IPKeys VTN. I verified that the agent can receive events from the VTN.

Unit tests:

➜ pytest      
===================================================================================== test session starts ======================================================================================
platform darwin -- Python 3.8.2, pytest-6.1.2, py-1.9.0, pluggy-0.13.1 -- /Users/boni407/Workplace/volttron-project/volttron/env/bin/python
cachedir: .pytest_cache
rootdir: /Users/boni407/Workplace/volttron-project/volttron, configfile: pytest.ini
plugins: asyncio-0.17.2, timeout-1.4.2
asyncio: mode=auto
collected 1 item                                                                                                                                                                               

test_openadr_ven_agent.py::test_handle_event_should_return_optIn PASSED                                                                                                                  [100%]

======================================================================================= warnings summary =======================================================================================

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules